Are Multi-Language Design Smells Fault-Prone? An Empirical Study

Nowadays, modern applications are developed using components written in different programming languages and technologies. The cost benefits of reuse the advantages each language two main incentives behind proliferation such systems. However, as number increases, so do challenges related to development maintenance these In situations, developers may introduce design smells (i.e., anti-patterns code smells) which symptoms poor implementation choices. Design defined coding choices that can negatively impact quality a software program despite satisfying functional requirements. Studies on mono-language systems suggest presence indicate higher risk future bugs affects comprehension, thus making harder maintain. multi-language fault-proneness is yet be investigated. this article, we present an approach detect context JNI We then investigate prevalence those their impacts fault-proneness. Specifically, 15 98 releases 9 open-source projects. Our results show prevalent selected projects persist throughout observe that, analyzed systems, 33.95% files involving communications between Java C/C++ contain occurrences smells. Some kinds more than others, e.g., Unused Parameters , Too Much Scattering Method Declaration . with often associated without smells, specific correlated others. From analyzing fault-inducing commit messages, also extracted activities likely smelly files. believe our findings important for practitioners it help them prioritize during